Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/epiverse-trace/tutorials/compare/md-outputs..md-outputs-PR-97

The following changes were observed in the rendered markdown documents:

⏱️ Updated at 2023-12-20 11:55:54 +0000

@Bisaloo after finishing with the edits in the PR, in parallel I merged #95.

This made visible the Update with Rebase option, so I did it, labelling the last commit as "force-pushed" as expected.

Then, in my local repo, I did git pull generating a local merge (not wanted). Please, look at the output messages, commit history, and screenshot from RStudio History pane:

~/tutorials (update-howto-rebase)
$ git pull
remote: Enumerating objects: 48, done.
remote: Counting objects: 100% (48/48), done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 48 (delta 38), reused 36 (delta 33), pack-reused 0
Unpacking objects: 100% (48/48), 14.52 KiB | 68.00 KiB/s, done.
From https://github.com/epiverse-trace/tutorials
 + c3aef90...9df13a4 update-howto-rebase -> origin/update-howto-rebase  (forced update)
   173598b..57d6a3d  gh-pages            -> origin/gh-pages
   46ef385..bc71b50  main                -> origin/main
   b189050..2137f56  md-outputs          -> origin/md-outputs
 + f34b77a...1ff0593 md-outputs-PR-97    -> origin/md-outputs-PR-97  (forced update)
Merge made by the 'ort' strategy.
 config.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

~/tutorials (update-howto-rebase)
$ git log
commit 541c73bbf3eae21850ac64bf02b6e817e2b4add9 (HEAD -> update-howto-rebase)
Merge: c3aef90 9df13a4
Author: Andree  Valle Campos <[email protected]>
Date:   Tue Dec 19 18:10:16 2023 +0000

    Merge branch 'update-howto-rebase' of https://github.com/epiverse-trace/tutorials
into update-howto-rebase

commit 9df13a4ced0584c166f2603d2d8a8d19bd523a47 (origin/update-howto-rebase)
Author: Andree  Valle Campos <[email protected]>
Date:   Tue Dec 19 18:00:01 2023 +0000

    add warning to do rebase only for one contributor per branch

At this moment I stopped and avoided pushing this content to GitHub. I imagine this would add a merge commit in the PR history and disallow the "rebase and merge" option.

To avoid this, you need to run git pull --rebase instead of a simple git pull.

You can also change your global settings via git config --global pull.rebase true so that git pull means git pull --rebase by default.

To avoid this, you need to run git pull --rebase instead of a simple git pull.

That step was the missing bit in the process. Thanks!